id: atis-pushback-and-taxi title: ATIS, Pushback and Taxi meta: Learn how to communicate pushback and taxi instructions with ATC in Infinite Flight. order: 2 contributor: babacar,lucaviness,planegeek,John370,KaiM #
ATIS, Pushback and Taxi #
ATIS Communication Summary #
Once spawned, the pilot will automatically be tuned to the ATIS frequency if it is currently staffed by a Controller. The current ATIS will continue to broadcast until the pilot tunes out.
-
As the ATIS is broadcast, it will appear at the top of your screen.
-
An on-screen notification will appear to inform you that you have been automatically tuned to an active frequency. You can tap it to dismiss the message.
-
The Communication button (headset icon) can be tapped to change frequencies, transmit/respond to ATC messages and to view the message log.
-
The top left corner of the communication box shows which airport the respective controller is transmitting from, the elevation, and the Controller’s frequency. The Controller’s facility and their display name is shown on the second line and the airport’s METAR is on the third line.
-
The back button can be used to select other frequencies or to tune out of the current frequency.
-
The last altitude, heading, speed and runway assignment issued by ATC as a reminder (these will be blank until instructions are transmitted).
-
The message log displays all communication history, double-tap it to just show your communication with ATC.
Tip
: When listening to the ATIS, plan your taxi route to the most likely runway that you will be sent to based on position and runway(s) in use for departure. Having a planned taxi route will help reduce your workload and make ground movement errors less likely!
ATIS Definitions #
Below are two tables that define the meaning of all REMARKS and NOTAMS that may be present in an ATIS broadcast:
+++ REMARKS
REMARKS | ATC Intention | Pilot Actions |
---|---|---|
No Intersection Departures | ATC require pilots to use the full length of the runway. | The pilot should hold short at the end of the runway. |
No Pattern Work | ATC is not accepting pattern work. | The pilot should not attempt to fly patterns at the airport, this does not include flying inbound for a touch & go landing provided the pilot then departs the airspace. |
Flow Control | ATC is controlling the departure rate. | The pilot should expect a delayed departure. |
Long Taxi | ATC may not send departures to the closest runway. | The pilot should expect to be sent to a runway that requires a long taxi time. |
Gate Hold | ATC needs to freeze all outbound ground movement. | The pilot should hold at their gate until the hold is lifted, do not send duplicate pushback requests. |
No Light Aircraft | Light aircraft (XCub, C172, P38, SR22, and Spitfire) are not allowed in the airspace or at the airport. | The pilot, if flying a light aircraft, must divert to or respawn at a different airport. |
Rolling Departures | ATC would like to expedite departures. | When cleared for take-off, the pilot should enter the runway and begin their take-off roll immediately. |
Flight Plan Required | ATC would like the pilot to file a flight plan before pushback/taxiing. | The pilot must file a flight plan before requesting pushback. |
Straight Out Departures | ATC would like aircraft to maintain runway heading until the altitude sent with the takeoff clearance is reached AND they are clear of traffic. | The pilot should fly straight until at the assigned altitude AND clear of all traffic before making any directional changes. |
Multiple Frequencies in Use | Controllers are using multiple frequencies to manage traffic. | The pilot should check the ATIS for the frequency to contact from their current position, and be ready to change frequencies at any time. |
Check Forum for Event Information | ATC is referring pilots to special instructions on the IFC pages (i.e. FNF, VARB Summit) | The pilot should check the forum before flying. |
SID/STAR Use Recommended | SID/STAR use is not essential for traffic management but is recommended. | The pilots should add a SID/STAR to their flight plan. |
SID/STAR Use Required | SID/STAR use is essential for traffic management or events. | The pilot must add an ATC preferred SID/STAR to their flight plan. |
+++
+++ NOTAMS
NOTAMS | ATC Intention | Pilot Actions |
---|---|---|
Event in Progress | An event is in progress. | The pilot may experience delays or, depending on the event, will not be allowed to participate. |
Size Restrictions in Place | The airport cannot handle certain sized aircraft. | The pilot should think about the size of their aircraft in relation to the airport. |
Low Visibility | Low visibility has been reported. | The pilot should expect low visibility. |
+++
Pushback Communication Summary #
Step 1
: Select the active Ground frequency
Step 2
: Tap “Request Pushback”
Tip
: If you are in a parking spot that does not require pushback, or in an aircraft that is not capable of pushback - then make sure to just request taxi when you are ready instead!
Step 3
: Tap “Send” or “Request Specific Runway” (if you do request a runway, the available runways will appear to select from, tap the desired runway for the request to be sent)
Tip
: If you are going to request a specific runway, make sure it is being used in the ATIS first!
Step 4
: When you receive your pushback clearance (or other communication from the Controller), the Communication button will flash amber and the message will appear at the top of the screen, tap the Communication button to “Reply” to the message
Tip
: When you receive your pushback clearance, you may be told to expect a specific runway - make sure to pushback in a direction that will allow you to taxi to the respective runway!
Taxi Communication Summary #
Step 1
: Tap “Request Taxi”
Step 2
: Tap “Active Runway” to send the message, or “Request Specific Runway” (if you do request a runway, the available runways will appear to select from, tap the desired runway for the request to be sent)
Tip
: If you are going to request a specific runway, make sure it is being used for departure in the ATIS!
Step 3
: When you receive your taxi clearance (or other communication from the Controller), the Communication button will flash amber and the message will appear at the top of the screen, tap the Communication button to “Reply” to the message
Pushback and Taxi Communication Tables #
Below are all the ATC commands that can be sent to pilots by a Ground Controller and what pilots can request or respond with:
+++ Pilot to Ground Controller
Request/Message | When to Send | When Not to Send |
---|---|---|
Request Taxi to an Active Runway | Sent when the pilot does not have a runway preference. | The pilot should not send this when they are actively pushing back. |
Request Taxi to a Specific Runway | Sent when the pilot has a runway preference. | The pilot should not request an inactive runway, determined by the current ATIS. |
Request Pushback | When the pilot wishes to pushback, they should request a pushback clearance. | This should not be requested if the user is piloting an aircraft without pushback capabilities (C172, C208, TBM-930, SR22, XCub, F18, F22, F16, F14, A-10, Spitfire, or P-38) or is in a parking space that does not require a pushback. |
Request Runway Crossing | If the pilot’s taxi route requires them to cross a runway, they must request permission to cross. The requested runway should be the same as the runway in use. | In any other circumstance. |
Request Frequency Change | The pilot should request a frequency change if they wish to change frequencies and have not yet been given a clearance to do so. | The pilot should not request a frequency change from Ground when they are taxiing to a runway. The frequency change is included in the taxi instruction (“contact Tower when ready”). |
+++
+++ Ground Controller to Pilot
Instruction/Message | ATC Intention | Pilot Actions |
---|---|---|
Taxi to Runway, Contact Tower when Ready | ATC has cleared the pilot to taxi to Runway XX. | The pilot should begin to taxi to the assigned runway. |
Pushback Approved | ATC has given the pilot clearance to pushback. | The pilot should pushback onto the taxiway. |
Hold Position | ATC wants the pilot to immediately stop their aircraft. | If at the gate, the pilot should wait until a pushback clearance is given. If the pilot is taxiing, they should bring the aircraft to a full stop and await the “Continue Taxi” instruction. |
Continue Taxi | ATC is lifting their “Hold Position” instruction. | The pilot can continue to taxi. |
Hold Short of Runway | ATC wants the pilot to hold short of the runway. | The pilot should hold their entire aircraft behind the hold short line. |
Cross Runway | ATC has cleared the pilot to cross the runway. | The pilot should cross the runway. If “Please Expedite” is included, the pilot should expedite crossing. |
Give Way to Aircraft | ATC wants the pilot to give way to another aircraft. | The pilot should yield to the respective aircraft. |
Expect Progressive Taxi Instructions | ATC will use progressive taxi instructions. | The pilot should continue as normal until given further instructions. |
Turn Left/Right Next Taxiway | ATC wants the pilot to turn left/right (respectively) at the next taxiway. | The pilot should turn left/right (respectively) at the next taxiway and continue taxiing until given further instructions. |
Continue Straight Ahead | ATC wants the pilot to continue straight on the taxiway they are currently on. | The pilot should stay on the taxiway until given further instructions. |
Make a 180 | ATC wants the pilot to make a 180º turn. | The pilot should turn around and await further instructions. |
Follow Aircraft Ahead | ATC wants the pilot to follow the aircraft ahead. | The pilot should follow the aircraft ahead until given further instructions. |
Continue Taxi at your Discretion | ATC wants to let the pilot know that they are no longer subject to progressive taxi instructions. | The pilot can continue their taxi at their discretion. If any other taxi instructions are given, they should follow those. |
+++